Improved Insights with Session-Level Traffic Splits

Yottaa runs a continuous test to evaluate the performance and business impact Yottaa is having on a website

For the most accurate assessment of how Yottaa’s optimizations impact eCommerce metrics like Conversion Rate, Bounce Rate, and Revenue (currently in Beta), Yottaa will begin splitting traffic between optimized and unoptimized at the session level rather than at the page view level.

Splitting traffic at the session level provides consistency because Yottaa either optimizes all the page views in a session, or leaves all pages unoptimized. For an optimized session, a site visitor will experience a faster site on every page of their session.

Splitting traffic at the session level provides a better measure of how much Yottaa's optimization affects session outcomes—did the session result in a conversion, and what was the purchase amount.

FAQs

No. This change has no impact on application sequencing rules. The only difference is that entire sessions will either be optimized or unoptimized for a cleaner analysis on the outcomes of sessions.

No. Only the way Yottaa chooses which pages to optimize or leave unoptimized will change. Yottaa will accurately report on optimized and unoptimized page views based on this determination.

In cases where performance rules are in place to withhold optimizations from Page Categories like the Checkout page (with sensitivity to third-party payment providers for example), splitting traffic at the session level respects those rules. That means that even in optimized sessions, Yottaa does not optimize page views if performance rules have explicitly excluded those pages from optimization.

Yes, the current percentage of unoptimized traffic split by page views will be kept the same when transitioning to session-level split. In other words, if the site previously had designated to keep 5% of page views as unoptimized, it will now have 5% of sessions as unoptimized.